Skip to main content
Version: 2.0

Key Decision Makers

As an engineering leader, you're often tasked with delivering solutions. But before a single line of code is written, before sprints are planned, and before velocity is measured, lies a crucial, often underestimated task: identifying and understanding who needs to be on board, and how they make decisions. This isn’t simply stakeholder management; it's about strategically assembling your “first team” – the individuals who will make or break your project, regardless of their formal position.

Too often, we default to org charts. While a starting point, an org chart tells you who reports to whom, not who actually influences outcomes. I’ve seen countless projects stalled not by technical challenges, but by a lack of buy-in from an unexpected, yet critical, stakeholder. This article focuses on how to identify these key decision-makers and navigate their influence effectively.

Beyond the Org Chart: Uncovering True Influence​

The biggest mistake engineering leaders make is assuming decision-making power aligns with title. Here's a framework to help you go deeper:

  • The Formal Authority: These are the individuals with explicit decision rights, usually managers and directors. However, true authority isn’t always about the title. Consider experience, political capital within the organization, and demonstrated ability to get things done. Sometimes a senior individual contributor carries more weight than a newly appointed manager.
  • The Informal Influencers: These individuals may not have direct authority, but their opinions carry significant weight. This could be a senior individual contributor, a long-tenured employee deeply embedded in the culture, or someone with a strong external network. I remember a project at a previous startup where a seemingly junior UX researcher consistently flagged usability issues that the entire development team dismissed. It wasn’t until the VP of Product specifically asked for her input on a critical feature that her concerns were finally addressed, and it saved us weeks of rework.
  • The “Veto Holders”: These individuals can single-handedly kill a project, even if others are on board. This could be a legal representative concerned about compliance, a security officer worried about vulnerabilities, or even a surprisingly vocal customer.
  • The Resource Controllers: Those who control essential resources – budget, access to data, critical infrastructure – wield significant power, even if they aren't involved in day-to-day decisions. For example, a project requiring access to a specialized database server might be held up indefinitely if the database administrator isn't convinced of its value or prioritizes other requests.

How to Identify Them:

  • Network Mapping: Talk to people. Informal conversations with team members, colleagues in other departments, and even administrative staff can reveal surprising connections and influence patterns.
  • Observe Meetings: Pay attention to who speaks up, whose opinions are sought, and whose concerns are immediately addressed.
  • Document Past Decisions: Research how similar projects were approved (or rejected) in the past. Who were the key players then?

The Founder's Dilemma: Control vs. Wealth & How It Impacts Your Team​

Noam Wasserman’s “The Founder’s Dilemma” highlights a crucial point: founders make fundamental choices about control versus wealth, and this directly impacts the decision-making dynamics within a company.

  • Control-Oriented Founders: Prioritize maintaining ownership and influence, often leading to slower growth but a strong, unified vision. Decision-making tends to be more centralized and conservative.
  • Wealth-Oriented Founders: Prioritize rapid growth and maximizing financial returns, often accepting dilution of ownership. This can lead to a more decentralized, agile decision-making process, but also potential conflicts.

Understanding where your company falls on this spectrum is vital. If the founders are highly control-oriented, you'll likely need to navigate a more rigorous, bureaucratic approval process. If they're wealth-oriented, you might have more autonomy, but need to be prepared for rapid change and potentially shifting priorities.

Building Relationships & Influencing Decisions​

Once you’ve identified your key decision-makers, the real work begins. It's not about manipulation; it's about building genuine relationships and understanding their perspectives.

  • Early Engagement: Involve them early in the process. Don’t surprise them with a finished product. Seek their input, address their concerns, and demonstrate that you value their expertise.
  • Tailored Communication: Different stakeholders require different communication styles. A technical architect will appreciate detailed specifications, while a marketing manager will focus on the customer impact. For example, when presenting a new feature to the architect, focus on the technical design and scalability. When presenting to the marketing manager, highlight the benefits to the user and the potential for increased engagement.
  • Framing the Benefit: Clearly articulate how your project aligns with their goals and priorities. What's in it for them? Focus on the value proposition, not just the technical details.
  • The “Pre-Mortem” Exercise: Before presenting a proposal, conduct a "pre-mortem." Assume the project has failed and brainstorm all the possible reasons why. This can help you anticipate objections and mitigate potential risks.

A Final Thought: The Human Element​

At its core, stakeholder management is about understanding people. Their motivations, their fears, their aspirations. Don’t treat them as obstacles to overcome; treat them as partners in achieving a shared vision. By investing the time and effort to build genuine relationships, you can navigate the complex web of decision-making and build a successful product, and a thriving team.

Next Steps:

  • Review your current project's stakeholder map.
  • Identify the key influencers who aren't on the org chart.
  • Schedule a quick check-in with a potential 'veto holder' to understand their concerns.

Suggested Visual:

[Insert a 2x2 quadrant here. Label the axes: "Influence (High/Low)" and "Support (High/Low)". Sections would be: "Engage" (High Influence/High Support), "Manage Closely" (High Influence/Low Support), "Keep Satisfied" (Low Influence/High Support), and "Monitor" (Low Influence/Low Support). This visually illustrates the need to prioritize efforts based on stakeholder characteristics.]